Software Testing through Evidence Gathering

An Evidence-based approach is using a best available evidence for making a thoughtful decision about a given set of problem. Evidencebased approach is an amalgamation of individually gained expertise with the evidences gathered through an organized research based approach. Its basic principles are that all practical decisions made should 1) be based on research studies and 2) that these research studies are selected and interpreted according to some specific norms characteristic for Evidence Based Practice[EBP]. Many software testing techniques are proposed to test various types of software and based upon the evidences gathered an effective testing methodology is adopted for a software. This is evidence based approach for software testing. The software techniques are classified on the basis of three criteria’s a) stepwise code reading b) performing functional testing by adopting boundary value analysis and c) all the statements are covered using structural testing. The study compares the strategies with respect to fault detection effectiveness and fault detection time complexity. In Evidence-based software engineering (EBSE), all the experiences are properly documented in order to inform software practice adoption decisions. In this research paper, the study factor would be the technology of interest. The technological specifications should be very detailed and not at a very high level of abstraction that is the software lifecycle and all the design methods should be properly read and documented and only then should the engineer collect evidences on it and design the software generation model. In this paper we analyze the gathered evidence so as to classify the testing strategies on the basis of applicability and types of testing. Priyanka Mathur et al 626 Various software testing strategies were studied in which white box testing and structural testing are the most preferred methods when using GA (Genetic Algorithm) and SA(Simulated Annealing) as a technique.